|
|
| Severity | Medium |
|---|---|
| Variants | All |
| WebsydianExpress
versions |
3.0 - 3.0.5 |
| Resolved in | v3.5 |
| Plex version | All |
| Category | API |
| Problem | After calling the APIServer.Session.Update, the SessionTimeOut
(which is not a parameter for the API) is set to 0).
This means that the next request for the session would report the session as being timed out. |
| Answer | An error in the function retrieving the current data for the session meant that the current session timeout was reported as 0. When the update for the session was made, this meant that the session timeout was changed to 0. |
| Workaround | Contact support@websydian.com to obtain a changed object that fixes this problem (fix# 41733).. |
Online documentation - Websydian v6.5